The Customization Wizard for the Subscriber Interface makes it possible for the data administrator to customize every page and email that a subscriber will see. This makes it easier to focus on your subscriber’s “touch points” and convey your organization’s message. This same customization can be applied to all of the pages related to a single dataset or to each individual page. For example, text for some lists can be in English, while text for others can be in French, or the entire look and feel of the signup page for an individual list can be different from all other lists in the dataset.
Each template in the Customization Wizard maintains two versions – a draft version and a production version. This allows you to test the draft version of the template, using varying conditions, before releasing it into production. Also, each screen of the Customization Wizard contains its own context-sensitive help. These instructions guide you through the Customization Wizard, describing each template or page, listing the placeholders used, and showing you how each template or page relates to the others.
To access the Customization Wizard, click on Recipient Warehouse >
Datasets from the Toolbar. The Recipient Dataset screen opens. Click on the name of the dataset that you want to customize. The Recipient Dataset Details screen opens. The right pane contains two tabs; click on the Membership Area Layout tab. If you have not customized your subscriber pages, then a general overview and introduction into the topic of membership area customization is displayed.
Note: If the subscriber pages are not customized, then LISTSERV Maestro will use the default setting for the visual layout and text.
Important: The introductory page is only shown if no customization has been previously performed. If any of the layout elements for the membership area have been customized, then the Membership Area Layout tab is shown with a list of customizable layout elements. For a dataset, the layout elements are divided into three tables – Templates, Pages, and Subscriber Notification Mails. For a list, the layout elements are divided into two tables – Pages and Matching Templates. For more information, see Section 2.2
Using the Membership Area Layout Tab.
If no customization has been done previously, then clicking on the Membership Area Layout tab displays a general overview, as described in the previous section. To refresh the tab and display a list of layout elements available for customization, click the
Select a Page link.
If customization has been done, then clicking on the Membership Area Layout tab takes you directly to the list of layout elements available for customization. The tab is divided into two panes. The left pane displays all of the recipient lists in the dataset in a tree-like structure, the dataset as the root and each list as a node.
A category is represented using a folder icon. Category folders with content (at least one list or subcategory in it) show a little “+” icon (if the folder is closed) or a “-” icon (if the folder is open). Click on the “+” or “-” icon to open or close a category folder. To select a node, simply click on it.
The right pane displays a list of all the customizable layout elements. For a dataset, the layout elements are divided into three tables – Templates, Pages, and Subscriber Notification Mails. For a list, the layout elements are divided into two tables – Pages and Matching Templates.
Note: The List Pages table contains the actual layout elements that can be customized for the selected list, while the Matching Templates table contains the layout elements of the dataset that the list belongs to. However, since the list pages, by default, make use of these templates, the templates have been included for convenience. When you make changes to the list templates, these changes apply to all lists in the datasets. To make changes to individual list pages, you must change the pages not the templates.
To start customizing a layout element, simply click on it. The Customize Page Layout screen opens and is divided into two panes. The left pane contains information on the selected page. The right pane contains two tabs – Draft Version and Production Version. For more information on this screen, see Section 2.3
Using the Customization Page Layout Screen.
To customize an advanced element, such as user messages or input validation errors, click on the
Advanced Customization link at the bottom of the tab. The Membership Area Layout tab refreshes and contains two tables – Message Page Texts and Input Validation Errors. Click on a link to customize that particular layout element. For information on editing messages and validation errors, see Section 2.6
Editing Informational and Error Messages.
Note: The
Advanced Customization link is only available if you’re customizing the subscriber pages for a dataset.
If at least the draft or production version of a layout element is customized (or both), then either an "equals" or a "not equals" sign is displayed between the two icons. This lets you know whether or not the current draft version is equal to the current production version. If both versions are not customized, then the equals-sign is not displayed because the two versions are the same.
If you have at least one layout element in the dataset where the draft version is different than the current production version, then the
Deploy icon allows you to deploy all these draft versions at once (either the ones in the dataset itself or all draft versions in the dataset and all its lists).
When changes are made to the dataset or lists after customizations have been made, the customized pages may become incompatible with the dataset. For example, if new fields are added to the dataset, then customized pages that do not include placeholders for these new fields are no longer valid. When this happens, the following symbols may be displayed instead of the symbols described above:
If the customization of any page is currently incompatible to the matching dataset, then the tab also displays an additional notification message about this and contains a link to a page where you can access all incompatible pages.
If customization has been done, then the Customize Page Layout screen can be accessed by clicking on the name of one of the layout elements on the Membership Area Layout Tab. For information on this tab, see Section 2.2
Using the Membership Area Layout Tab.
In the upper right corner of the Customize Page Layout screen, the Currently Customizing drop-down menu allows you to easily switch from customizing a dataset to customizing a list. To customize the membership area layout for the dataset, click the drop-down menu and select
Membership Area Layout. This layout is shown by default if this is your first time accessing this screen. To customize the list(s) in the dataset, click the drop-down menu and select the list you want to customize (i.e. if you have a list named XYZ, then select
Layout of List XYZ).
The Customize Page Layout screen is divided into two panes. The left pane is where you select the page or template that you want to customize. The default is the Membership Area Header/Footer page. To change, simply click the
Selected Page/Template drop-down menu and select a different page or template to work with. From this menu, you can also select to customize notifications, messages, or errors.
|
•
|
If you selected a template page, normal page, or a notification email, then a short description of the selected layout element is displayed.
|
|
•
|
If you selected a message text for a message group, then a list of available messages for that group is displayed. Click on one of the messages to select it as the layout element you want to customize (or view). When you initially select a message group from the drop-down menu, the first message in the group is selected by default.
|
|
•
|
If you selected an input validation error for an error group, then a list of available errors for that group is displayed. Click on one of the errors to select it as the layout element you want to customize (or view). For each error group, there is an Error Group Header/Footer layout element that defines a common opening and closing text that is shared by all of the errors in this group. This header/footer appears first in the list of errors for the group and is selected, by default, when you initially select an error group from the drop-down menu.
|
The right pane contains two tabs – the Draft Version tab and the Production Version tab. The production version is the version that subscribers, who access the membership area pages, actually see. The draft version, on the other hand, is not visible to the subscribers. This means that you can safely make any changes to the draft version without them becoming immediately visible. For example, you may want to customize one page after the other by editing their draft versions; but, you want to make the customized versions available all at once, after you have finished with all pages. Or, you may want to experiment a bit with the layout, without disturbing the actual production versions that subscribers see. Only when you finally deploy the draft version as the new production version will your changes become visible to subscribers.
|
•
|
If you selected a template, then the preview displays the page as a normal HTML page, as it would appear in the subscriber’s browser. Since the page being displayed is a template, a rectangular placeholder frame is used at the location where the actual content will appear when the template is used by a page.
|
|
•
|
If you selected a normal page, then the preview displays the pages as a normal HTML page, as it would appear in the subscriber’s browser.
|
|
•
|
If you selected a subscriber notification email, then the preview displays the email in text format, and also displays the other email attributes like the From address, Subject line, and language charset that will be used. It also displays the currently used "maximum line length", i.e. the line length used to wrap the text with.
|
|
•
|
If you selected a message page text, then the preview of the message page texts is shown by displaying the actual message page (which, by itself, is one of the normal pages, see above) as a HTML page, as it would appear in the browser of the subscriber with the currently selected message in place.
|
|
•
|
If you selected an input validation error, then the error is shown by displaying a default page with the selected error message displayed on this default page.
|
|
•
|
View Source – Click to view the source of the current production version.
|
|
•
|
Deploy as Production Version – Click to deploy the current draft version as the new production version. This will make a copy of the current draft version of the selected layout element and write it into the element's production version, making this the version of the selected element which subscribers actually see. The draft version remains unchanged.
|
|
•
|
Copy from Production Version – Click to make a copy of the current production version and use it as the new draft version. This will overwrite all current changes to the draft version. The production version remains unchanged.
|
|
•
|
Reset to System Default – Click to reset the current draft version to the LISTSERV Maestro system default. This will overwrite all manual changes to the draft version and will reset it to its default. The production version remains unchanged.
|
|
•
|
Show Preview – Click to show the preview of the current production version.
|
|
•
|
Header/Footer Template – This comment shows how many pages (in the dataset and its lists) that are currently using the header/footer template (i.e. pages that do not have a header/footer defined of their own but are inheriting the template). Click the Details link to view a detailed list of pages using this template.
|
|
•
|
Any of the List Page Templates – The first comment shows if the template page inherits the header/footer template (see above) or if the header/footer is defined locally on the list page template. The second comment (below the first one) shows how many list pages are currently using the corresponding template (i.e. pages that only define the layout of the actual list profile fields locally, but also inherit the rest of the page layout from this template).
|
|
•
|
Any of the Normal Pages – The comment displays if the page inherits the header/footer template (see above) or if the header/footer is defined locally on the page.
|
|
•
|
Any of the Message Page Texts – The comment describes the currently selected message and the circumstances under which it is displayed to the subscriber.
|
|
•
|
Any of the Input Validation Errors – The comment describes the currently selected error message and the circumstances under which it may occur. Also, unless the current message is already the error-header/footer of the error group, then it provides a link to select the error-header/footer for the current error group. By editing the error-header/footer, you can provide all errors in one error group with the same opening and closing texts.
|
Additional controls may also appear, allowing you to simulate certain system states so you can verify their impact on the actual preview. These controls vary depending on the layout element selected, and only a few elements offer them. For information on these controls, please see the online help.
Templates contain the default layout and design for the subscriber pages in the membership area. Templates are used to give a uniform look to your subscriber pages and can help you customize many pages all at once. By inheriting parts from the template, repetitious work can be saved on individual pages, and a change to the template will automatically apply to all pages that use the template.
Pages are specific subscriber pages for the dataset/list. They can be customized individually, with no impact on others, or they can be customized by inheriting parts from a template.
If you choose to edit the current draft version of a template or page (by clicking the Edit Source icon), then you will need to edit the HTML source code. This HTML code also includes the placeholders as specified in the left pane (see Section 2.7
Placeholders). It also defines the general layout of the page as well as the design style (see Appendix A:
Custom Styles and HTML Tags). The HTML code is edited in the main edit field in the center. Above the edit field, a drop-down list is used to define what part of the page is to be edited (in the edit field), and which part is to be inherited from the applicable page template (this drop-down list is not available for the Membership Area Header/Footer Template). By inheriting parts from the template, repetitious work can be saved on the individual pages, where the HTML code that is already defined in the template does not need to be included. Also, a change to the template will automatically apply to all pages that use the template. To submit the changes, click
[OK]. To cancel editing without submitting any changes, click
[Cancel].
|
•
|
Copy from Production Version – Click to make a copy of the current production version and use it as the new draft version. This will overwrite all current changes to the draft version. The production version remains unchanged.
|
|
•
|
Reset to System Default – Click to reset the current draft version to the LISTSERV Maestro system default. This will overwrite all manual changes to the draft version and will reset it to its default. The production version remains unchanged.
|
The Membership Area Header/Footer Template is a common template that is shared by all pages in the membership area; therefore, any changes to this template will automatically affect all pages. Because of this, the Membership Area Header/Footer template is the ideal place to start customization, providing a common frame or layout for every page. For example, you can add a common header or footer, or you can define common HTML styles, colors, and fonts.
If you are viewing the Membership Area Header/Footer template in the Customize Page Layout screen, then the
Details link is available. Click this link to see a list of the pages that are using this template. To view a specific page in the list, simply click the
Open link next to that page. To exit the list and return to the preview of the template, click the
Back to Template link.
To edit the template, click the Edit Source icon on the Draft Version tab of the Customize Page Layout screen. Then, enter/edit the HTML source code. This HTML code also includes the placeholders as specified in the left pane (see Section 2.7
Placeholders). When editing the Header/Footer Template, Cascading Style Sheets (CSS) should be used to customize the style of the page. The HTML code for the default pages (pages that are not customized) uses a few common HTML tags as well as custom style classes, whose look can be defined with a customized style sheet. For a list of these custom styles and HTML tags, see Appendix A:
Custom Styles and HTML Tags.
The Membership Area Page is the home page of the dataset and is the first page that the subscriber sees after logging in. This page is divided into two sections – My List and My Profile – and contains links that let the subscriber navigate between these two sections.
Under certain circumstances, the Membership Area Page shows additional welcome messages to the subscriber. Normally, there is no welcome message displayed. However, the following situations have their own welcome message:
|
•
|
For a Confirmed Member (Default) – The page is viewed in its default state as seen by normal confirmed members.
|
|
•
|
For a Confirmed Member (LISTSERV not available) – Same as Confirmed Member (Default) (see above); however, this state simulates that LISTSERV is not available (LISTSERV itself or the network is down). This situation may impact the presentation of Linked LISTSERV Lists; therefore, this simulated state is only available if there are any Linked LISTSERV Lists in the dataset.
|
|
•
|
For a Confirmed Member with the List-Subscription-Welcome-Message – The page is viewed by a confirmed existing member who has just subscribed to an additional list from outside of the Membership Area (via the special external subscribe pages). At the end of the external subscribe, the member was automatically logged into the Membership Area and was directed to this page, which is the first page the member sees after the system has accepted the external subscription. Therefore, this page takes over the job of informing the member of the success of their external subscribe, and displays a message that they are now freshly subscribed to the given mailing list.
|
|
•
|
For a Confirmed Member with List-Subscription-Welcome-Message (LISTSERV not available) – Same as Confirmed Member with List-Subscription-Welcome-Message (see above); however, this state simulates that LISTSERV is not available (LISTSERV itself or the network is down). This situation may impact the presentation of Linked LISTSERV Lists; therefore, this simulated state is only available if there are any Linked LISTSERV Lists in the dataset.
|
|
•
|
For an Unconfirmed Member with Membership-Unconfirmed-Message – The page is viewed by a member who has still not confirmed their membership (via the confirm link in the double opt-in confirmation mail). In this case, a message is displayed reminding the member of the still unconfirmed state of their membership, and how to confirm it.
|
|
•
|
For an Unconfirmed Member with Join-Welcome-Message – The page is viewed by a "new" member who has just joined the Membership Area (so they are viewing this page for the very first time) and has not yet confirmed the membership. A similar reminder as above is displayed and a "Welcome to the Membership Area" message is also displayed.
|
|
•
|
For an Unconfirmed Member with List-Subscription-Welcome-Message – The page is viewed by a "new" member who has not only just joined the Membership Area (so they are viewing this page for the very first time), but has also subscribed to the first list at the same time and not yet confirmed the membership. A similar reminder and welcome message as above is displayed, but the welcome message is not only a general "Welcome to the Membership Area" message, but a more specific message about the mailing list that the member has just subscribed to.
|
To simulate these different welcome messages, click the State drop-down menu and select one of the choices described above. In addition, the right pane displays the Membership Area State tab, which lets you define additional settings in order to simulate different subscriber states.
The Membership Area State tab is a special tab that is only available if the currently selected layout element is the Membership Area Page. The controls on this tab can be used to simulate a certain subscriber and list state, impacting the preview of the Membership Area Page shown when the Draft Version tab or Production Version tab are selected. Using the Membership Area State tab, different states can be experimented with and tested in order to see how each state impacts the membership area page layout.
|
•
|
Subscribed State – Check the Subscribed option to simulate how the page looks for a member who is subscribed to the given list. Uncheck this option to simulate a member who is not subscribed to the list.
|
|
•
|
Public Access State – Click the drop-down menu and select the access state to simulate for the list. With this, how the page looks to a member can be verified (with the subscription state defined via the Subscribed option, see above) if the list has the selected state. The possible states are Open to everyone, Access for subscribers only, or No public access.
|
|
•
|
Maintenance State – Check the Closed for maintenance option to simulate that the given list is currently closed for maintenance. Uncheck this option to simulate that the list is not closed. With this, you can verify how the Membership Area Page looks to a member (with the subscription state defined via the Subscribed option, see above) when the list is closed for maintenance and when it is not.
|
To edit a notification email, click the Edit Source icon on the Draft Version tab of the Customize Page Layout screen.
The Draft Version tab now contains a a new drop-down menu appears at the top of the tab. This option gives you the ability to create an HTML version of the email along with a plain text alternative.
To create an HTML message with the plain text alternative created automatically, click the drop-drown menu and select
Use HTML below for HTML part and generate the Plain Text version automatically.
To create an HTML message with a separate plain text alternative, click the drop-down menu and select
Define separate HTML and Plain Text version. When this option is selected, two tabs will appear for defining the body’s content.
|
•
|
Sender Name – Enter the name that is to be used as the sender name. Do not use an email address; instead, enter a real name. This value is optional; if nothing is supplied, then the List Administrator’s address (from the dataset definition) will be shown in the From: field.
|
|
•
|
Subject – Enter the subject line that is to be used for this notification email. In the left pane, there is a list of all placeholders that may be included in the subject line. These placeholders will be replaced with suitable values before delivery. Enter the placeholder manually into the subject line or click on the link to automatically add the placeholder at the current cursor position.
|
|
•
|
Body – The main edit field for the email body. When defining the email body content, use the drop-down menu to determine what type of content you’ll be defining. To use the email’s body template and provide your own body content, select Notification mail body template inherited, body define below. To create an all new email (without template), select All content defined below.
|
Note: When defining the HTML and plain text versions of the email separately, then this drop-down menu is available on both the HTML and Plain Text tabs.
|
•
|
[Upload HTML] – Click to upload an HTML file into the body of the email.
|
|
•
|
Language Charset – Select the language charset (character encoding) to use for the email delivery. The charset should match the language (or the special non-ASCII characters, if any) that were used in the body.
|
|
•
|
Copy from Production Version – Click to make a copy of the current production version and use it as the new draft version. This will overwrite all current changes to the draft version. The production version remains unchanged.
|
|
•
|
Reset to System Default – Click to reset the current draft version to the LISTSERV Maestro system default. This will overwrite all manual changes to the draft version and will reset it to its default. The production version remains unchanged.
|
To submit the changes, click [OK]. To cancel editing without submitting any changes, click
[Cancel].
To change the format of all notification emails for this dataset, click on the Change link at the bottom of the
Subscriber Notification Mails section of the Subscriber Pages and Templates table.
|
•
|
Evaluate the following condition to decide if a subscriber receives HTML or plain text. If this is selected, then select the boolean field and its value from the drop-down menus. When selected, then HTML emails will only be sent to those subscriber that meet the requirements of this condition. Those subscribers who do not meet these requirements will receive a plain text email.
|
Once you finished, click [OK]. The new format status will be displayed at the bottom of the
Subscriber Notification Mails section of the table next to the
Change link. This format status will be applied to all notification emails in the dataset.
To edit a message text or an input validation error, select the message group or error group you want to edit, and then select the specific message/error from the list of available elements in the left pane of the Customize Page Layout screen. Once you’ve selected the message/error, then click the
Edit Source icon on the Draft Version tab. Finally, enter/edit the information in the following fields, if applicable:
|
•
|
Title – This field is only available for informational messages. Enter the text that is to be used as the title of the message. HTML tags can be used to format it (see Appendix A: Custom Styles and HTML Tags). Below this field there is a list of all placeholders that may be included in the title. These placeholders will be replaced with suitable values. Enter the placeholder manually into the field or click on it to automatically add the placeholder at the current cursor position.
|
|
•
|
Text – This field is available for informational messages and input validation errors. Enter the text that is to be used as the actual message. HTML tags can be used to format it (see Appendix A: Custom Styles and HTML Tags). Below this field there is a list of all placeholders that may be included in the message. These placeholders will be replaced with suitable values. Enter the placeholder manually into the message or click on it to automatically add the placeholder at the current cursor position.
|
|
•
|
Header or Footer – These fields are only available for the header/footer page of an input validation error. Fill out each with the corresponding text (and HTML code) that is to be used as the opening text (header) and closing text (footer) of each error message in this group. For example, by default the header of each error group contains an opening <ul> tag and the footer contains the matching closing </ul> tag; together, they define an unnumbered list in HTML. Consequently, the default error messages all start with <li> to constitute a bullet in this list. For a list of HTML tags, see Appendix A: Custom Styles and HTML Tags.
|
|
•
|
Copy from Production Version – Click to make a copy of the current production version and use it as the new draft version. This will overwrite all current changes to the draft version. The production version remains unchanged.
|
|
•
|
Reset to System Default – Click to reset the current draft version to the LISTSERV Maestro system default. This will overwrite all manual changes to the draft version and will reset it to its default. The production version remains unchanged.
|
To submit the changes, click [OK]. To cancel editing without submitting any changes, click
[Cancel].
Placeholders are used in pages and templates to represent parts of the page or template that are defined elsewhere and will be filled in with their final values when the page is displayed to the subscriber. Placeholders come in different types:
|
•
|
Profile placeholders represent the data fields that make up the “profile” of individual dataset members and list subscribers. The syntax for the profile placeholder of a data field called “XYZ” is {{maestro:profileXYZ}}. When a page is displayed to the subscriber, then the placeholder will be replaced by the value of XYZ for that subscriber. The display name defined for the field is represented by the {{maestro:labelXYZ}} placeholder. Changing the display name in the dataset definition will automatically update all the pages that use this placeholder.
|
|
•
|
Structural placeholders represent pages or parts of pages. For example, in the header/footer template, the {{maestro:body}} placeholder represents the “body” part of pages that inherit the header/footer template. In a fully customized page, the {{maestro:body}} placeholder marks the beginning of the body part of the page, and the {{/maestro:body}} placeholder marks the end of the body part. If the page is subsequently changed to inherit the header and footer from the header/footer template, then only the part of the page between these two placeholders will be retained.
|
|
•
|
Conditional placeholders mark the beginning and end of parts of the page or template that are displayed under certain conditions. For example, on certain pages and templates, the {{maestro:validationErrorsPresent}} and {{/maestro:validationErrorsPresent}} placeholders surround the text and code that will be used only if validation errors have been detected. The {{maestro:validationErrors}} placeholder, which can only be used within this conditional block, will be replaced by the relevant validation error text, as defined in the error message templates.
|
When you are editing a template or page, then the placeholder tree structure is displayed. This structure defines the placeholders that can be used for the customization of the selected page or template. Placeholders are divided into two categories – Free Placeholders and Restricted Placeholders. Free Placeholders may appear anywhere on the page; Restricted Placeholders, when used on a page, must conform to the same tree structure that is shown in the left pane.
|
•
|
Free Placeholders – Free placeholders may appear anywhere on the page, even inside other placeholders. They are always optional, which means that you can include them, but do not have to.
|
|
•
|
Optional Restricted Placeholders – Restricted placeholders must adhere to their parent-child structure. This means that all top-level restricted placeholders (i.e. the ones without any further parents in the tree structure) can be used anywhere on the page, at top level (not inside other placeholders), while sub-level placeholders can only be used on the page if they appear inside their matching parent placeholder (as defined by the tree structure). An optional restricted placeholder can be included on the page, but does not have to be included. If such a placeholder is omitted, all its children (if any) must be omitted too.
|
|
•
|
Mandatory Restricted Placeholders – The same rules about restricted placeholders as already described above for optional restricted placeholders apply here too, but placeholders of this type are mandatory (i.e. they must appear on the page); otherwise, the customization is not accepted by the system. Mandatory placeholders are also marked by using a bold font for their name.
|
In the tree structure, placeholders with further children are preceded by a “+” symbol (if the children are currently not visible) or “-” symbol (if the children are currently visible). Click on the “+” or “-“ symbol to make the children visible or to hide them.
If you click on a placeholder (i.e. its symbol or name), then the placeholder is selected and shown inside of a blue box, with an additional short description of the placeholder. Therefore, if you do not remember what a certain placeholder does exactly, or why it is required or not, simply select the placeholder to see this description. If you are editing the draft version, the box also contains a
small green arrow icon. When you click the arrow, the placeholder tag for the placeholder will automatically be inserted into the page code (in the right pane) at the current cursor position. This arrow is not available when viewing the source of the production version.
If you want to use a placeholder on the page, then you will need to write it using the special placeholder tag syntax. The syntax is slightly different depending on whether or not the placeholder contains a body or attributes.
|
•
|
Without Body – The placeholder tag consists of a single tag and looks like this:
|
|
•
|
With Body – The placeholder tag consists of an opening and closing tag, with the placeholder body between the tags, such as:
|
{{maestro:NAME}}
...placeholder body goes here...{{/maestro:NAME}}
where you must replace "NAME" (in both the opening and closing tags) with the placeholder name (as shown in the tree). Placeholder names are case sensitive. The body, which is only outlined in the example above, can be any further HTML code and may also contain linebreaks (i.e. stretch over several lines or paragraphs). Also, the placeholder tags of the placeholder’s children must appear within this body. For example, if you have a tree definition like this:
{{maestro:validationErrorsPresent}}
{{maestro:validationErrors}}
{{/maestro:validationErrorsPresent}}
|
•
|
With Attributes – Some placeholders may additionally contain attributes, using the following syntax:
|
{{maestro:NAME ATTRIBUTE="VALUE"}}
where "NAME" is to be replaced as shown above, and "
ATTRIBUTE" and "
VALUE" are to be replaced with the attribute name and value.
{{maestro::NAME ATTR1="VALUE1" ATTR2="VALUE2" ATTR3="VALUE3"}}
This table lists the attributes that may be used with subscription status profile field placeholder. These placeholders are only available for Hosted Recipient Lists and Hosted LISTSERV Lists.
This table lists the attributes that may be used with subscription type profile field placeholders. These placeholders are only available for Hosted LISTSERV Lists with digests enabled.
Since each profile field may appear on several pages (for example, on the External Subscribe pages and on the Internal Edit Profile page), it would become burdensome to have to specify the display attributes for a given profile field on each page that this field appears on. To avoid this, it is possible to define defaults for the attributes of all profile fields of a dataset or list. The default attributes for a given profile field will be used whenever the profile field's placeholder appears on a page, unless that placeholder appearance defines its own attributes. In other words, if a profile field placeholder appears on the page without any attributes, then the default attributes will apply. If the placeholder on the page already contains individual attributes, then the default attributes are not used and the individual attributes apply (but only on this page).
To define the default attributes for a profile field, click the Profile-Placeholder Default Attributes link at the bottom of the Pages table (on the Membership Area Layout tab while customizing the subscriber pages of a dataset or list). The Profile-Placeholder Default Attributes information is displayed. (For more information on placeholders and their attributes, see Section 2.7
Placeholders.)
Click on the name of the field you want to customize. The Edit Default Attributes screen opens; specify the attributes in the same way as for specifying them in the placeholder, when including the placeholder in the customized HTML code.
For example, assume there is a profile field called "FNAME" and that it should display with an edit field of size "
40". Either include the placeholder "
{{maestro:profileFNAME size="40"}}" directly on the page, or include the placeholder without attributes ("
{{maestro:profileFNAME}}") on the page and define the default attribute "
size="40"" on the Edit Default Attributes screen.
Note: The default versions of all membership area pages (the versions that are used if no customized versions are provided) all use the profile field placeholders without any individual attributes; therefore, any pages that are displayed in their default state will also use the profile-placeholder default attributes you define.
When creating the message content for an email job, you can now add a special system drop-in that will direct your subscribers to the External Profile Edit Page. This page will let your subscribers update specific profile fields without logging into the Membership Area.
The External Profile Edit Page is a dynamic page that queries certain profile fields from the subscriber. The fields that are queried by the page during a visit depends on the parameters in the URL by which the page was accessed. And, the parameters in the URL in turn are created by the
ProfileEditPageURL system drop-in depending on the field names that you include in the
FIELDNAME_LIST of that system drop-in.
With the examples of above: If you are planning to use {{*ProfileEditPageURL STREET,ZIP_CODE,CITY}} to query the address data of the subscriber, and you first want to check that the page will look correctly if these three profile fields are displayed, then go to the External Profile Edit Page, check the boxes for STREET, ZIP_CODE, and CITY, uncheck all other boxes, and then click
[Apply]. The preview will then show the page just as it will look to subscribers if you use the system drop-in with STREET, ZIP_CODE, and CITY.
|
2.
|
If the {{*ProfileEditPageURL FIELDNAME_LIST}} system drop-in is used in a mailing to a dataset, then FIELDNAME_LIST must only contain profile fields that are fields of the dataset. It can not contain any fields that belong to any of the HRLs or HLLs in the dataset.
|
The Subscriber Interface for the External Profile Edit Page reflects this: just above the previously mentioned checkboxes, you have a
Preview page with profile fields of drop-down menu that allows you to select which profile fields you want to see. If you select
The Dataset, then you will only see checkboxes for the dataset profile fields. This simulates the situation when you use the system drop-in in a mailing to the dataset. If you select
The “LIST”, then you will see all checkboxes for list XYZ plus all of the dataset. This simulates the situation when you use the system drop-in in a mailing to list XYZ where you can use all combined profile fields from the list and dataset in
FIELDNAME_LIST.
